Skip to content

Conversation

@koletzilla
Copy link
Contributor

Summary

Checklist

  • Delete items not relevant to your PR

@koletzilla koletzilla requested review from a team as code owners January 9, 2026 17:58
@vercel
Copy link

vercel bot commented Jan 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
clickhouse-docs Ready Ready Preview, Comment Jan 12, 2026 11:37am
3 Skipped Deployments
Project Deployment Review Updated (UTC)
clickhouse-docs-jp Ignored Ignored Jan 12, 2026 11:37am
clickhouse-docs-ru Ignored Ignored Preview Jan 12, 2026 11:37am
clickhouse-docs-zh Ignored Ignored Preview Jan 12, 2026 11:37am

@koletzilla koletzilla changed the title dbt-clickhouse: Explain new ´on_schema_change´ config available for MVs [dbt] Explain new ´on_schema_change´ config available for MVs Jan 9, 2026
@koletzilla koletzilla changed the title [dbt] Explain new ´on_schema_change´ config available for MVs [dbt] Explain new 'on_schema_change' config available for MVs Jan 9, 2026
> you will encounter the following warning:
`Warning - Table <previous table name> was detected with the same pattern as model name <your model name> but was not found in this run. In case it is a renamed mv that was previously part of this model, drop it manually (!!!) `

#### How to iterate the target table schema {#how-to-iterate-the-target-table-schema}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title and text use “iterate the target table schema.” feels a bit unclear to me, do you happen to have other suggestions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants